Enhanced cell global identifier-based handover from an eNodeB to a home eNodeB

ABSTRACT

Examples are disclosed that facilitate using enhanced cell global identifier to effectively manage the handover of cellular communication services for a mobile device in an LTE network from a source, or serving, evolved Node B (eNB) to a target home evolved Node B (HeNB). The increased use of HeNBs to provide service to mobile devices creates issues for the management of tracking area identifiers associated with the eNB and HeNBs and may increase tracking area update (TAU) signaling in the cellular network. The handover of a mobile device moving from an eNB coverage area to a neighboring HeNB coverage area is managed without use of a tracking area identifier by using enhanced cell global identifiers assigned to the respective HeNB. The following provides examples for minimizing the burden on the network devices to manage the administration of TAIs and that may reduce TAU signaling in the cellular network.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/556,825, filed Dec. 1, 2014, which is incorporated herein byreference.

BACKGROUND

Wireless communications services and portable devices that use suchservices continue to increase in popularity. The wireless networks andmobile devices support a wide array of voice and data communicationfunctions. A key feature of such devices and the wireless networks ismobility, that is to say, the ability of the user with the device tomove freely from place to place and still operate the device to obtainwireless network services.

The capability of a cellular network to manage the movement of UserEquipment (UE) within the cellular network is referred to as mobilitymanagement. The network device that manages UE mobility management in aradio access network (RAN), such as a Long Term Evolution (LTE) RANnetwork, may be referred to as a mobility management entity (MME). TheMME uses identifiers related to the respective UEs as well as variousidentifiers related to the cells in which the respective UEs are locatedand/or the cells that UEs may next roam into. The cellular serviceswithin the cells are provided by base stations that provide the cellularservices to the UE over an air interface. As the UE travels from onecell to another, the MME manages the delivery of cellular services tothe respective UE. In order to efficiently manage the delivery ofcellular services, each base station is assigned an identifier which aserving MME tracks in order to reach out to an idle UE. The generalindication is a tracking area, which refers to a location being servicedby a base station. The purpose of a tracking area designation is so theMME does not have to scan an entire network to locate a UE. A trackingarea may identify one or a group of cells. The UE assists the MME byreporting to the MME TA in which the UE is located. In addition, the UEmaintains a list of TAs that were used or identified by the UE. Forexample, while idle the UE may detect base station reference signals andread overhead messages transmitted by the detected base station. Theoverhead messages include identifying information of the respective basestations. In addition, the UE may make measurements, such as receivedsignal strength, of the respective reference signals. The identifyinginformation in the overhead messages and the respective measurements maybe stored by the UE for future use.

One of the identifiers included in the overhead messages is a trackingarea identifier (TAI). In general, TAIs are identifiers of areas inwhich a UE has been serviced by one or more radio base stations, such asan evolved Node B (i.e., eNB). The number of TAIs is limited becauseeach cellular provider only has 65535 tracking area codes available, andusually a large number of the TAIs are pre-allocated to the trackingareas (TAs) of the cellular provider to accommodate tracking areas thatcorrespond to fixed eNBs; therefore, a small pool of TAIs is availablefor the more mobile HeNBs. As a UE travels closer to another eNB, adetermination is made whether the UE would be better served (i.e.,receive better quality of service) from a neighboring or target eNB ascompared to the service that the UE is currently receiving from theserving, or source, eNB. The source eNB may make a determination that UEis better served by a neighboring eNB. The MME is informed via a handoffrequest of the impending eNB change from a source eNB identified by afirst TA to the target eNB of a second TA. The transfer of service fromthe source eNB to the target eNB is referred to as a “handover.” In casethe source and target eNBs have different TAIs, a Tracking Area Update(TAU) procedure may get initiated by the UE so that the MME can updateand store the new location (i.e., TAI) of the UE. This will help the MMEto reach out to an idle UE based on the UEs last known location or TA incase some data needs to be delivered to that UE.

The handover process is covered by telecommunication standards, such asthe current standard (i.e., 3GPP Release 12 (R12)). At a high level andaccording to the standard, there are three broad processes thatconstitute handover: 1) handover preparation, 2) handover execution, and3) handover completion. The particular handover process discussed hereinis a preliminary operation related to the handover preparation. Afterthe handover preparation process discussed herein, the two otherhandover operations, handover execution and handover completion, thatmake up the broader handover operation occur. The handover execution andhandover completion processes are unaffected by the improvements to thehandover preparation discussed in the detailed description of theexamples.

Similar to the revolution in UE devices becoming more powerful yet morecompact, devices that offer the substantially the same functionality asthe base stations described above are also becoming more powerful andcompact. These base station-like devices, referred to as Home eNBs(HeNBs) are portable, provide cellular services to multiple UEs, and maybe installed by consumers via an internet connection to a cellularservice provider server. Once the HeNB is provisioned with therecommended parameter settings provided by a cellular service providerserver, the HeNB provides an air link to the cellular communicationnetwork of the cellular service provider to which the UE may attach, andreceive cellular service. The HeNB communicates with the MME in the samemanner as an eNB. In effect, the HeNB is another eNB in the cellularnetwork. As a result, the MME has to manage and service the UEs that maybe in the area of the HeNB. The HeNBs typically provide cellularservices to a small coverage area, often referred to as a femtocell.These femtocells are small geographical areas, and are typically inareas where cellular service from an eNB is poor, such as indoorlocations, such as a building or urban canyon that are also not high UEtraffic areas and the like. However, an HeNB may begin providingservices within a coverage area of an eNB. As such, the HeNB fallssubstantially in the TA of an eNB.

A TA is identified by a tracking area identifier (TAI). The TAI of eachbase station, eNB and HeNB, under control of the MME is provided to theMME. There are a limited number of TAIs. The implementation of the TAImanagement concept did not take into account the implementation ofHeNBs. As such, the type and deployment strategy for HeNBs is differentand leads to a problem with the limited TAIs. A HeNB is a small scaleshorter range device intended for deployments in users/customerspremises (homes, offices, or the like). As a result, HeNBs are likely tobe deployed in larger numbers and the cellular service provider is lesslikely to be able to control or know of the geographic coverage areasuch HeNBs provide. An MME routing the handover signaling messages basedprimarily on the TAI of the target HeNB would tax the limited TAIresources of the cellular service provider.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 is a high-level functional block diagram that illustrates anexample environment 100 for implementing examples of the describedsubject matter.

FIG. 2 illustrates an example allocation of tracking area identifiersaccording to the described subject matter.

FIG. 3A is a process diagram showing an example of a mobile devicehandover request according to an example of the described subjectmatter.

FIG. 3B is a high-level functional block diagram of an example of anetwork device and a supported network device configuration according toan example of the described subject matter.

FIG. 4 is a high-level functional block diagram of an example of a HeNBgateway configuration for implementing examples of the described subjectmatter.

FIG. 5 is a simplified functional block diagram of a computer that maybe configured as a network device, such as a mobility management entityor a HeNB gateway according to an example of the described subjectmatter.

DETAILED DESCRIPTION OF EXAMPLES

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent that the presentteachings may be practiced without such details. In other instances,well known methods, procedures, components, and/or circuitry have beendescribed at a relatively high-level, without detail, in order to avoidunnecessarily obscuring aspects of the present teachings.

The described examples are implemented in a LTE network environment,although the enhanced mobility may be utilized in wireless networksbased on other mobile wireless technologies. The LTE networkenvironment, in the examples, operates according to a Third GenerationPartnership Project (3GPP) standard (i.e., the LTE standard) for mobilenetwork technology. The LTE standard describes requirements for mobilecommunications systems in evolved or advanced cellular broadbandtechnologies. Such requirements include Evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN), which is a wireless network technology that implements ahigh-speed radio access technique to meet increased network demands,including improving user throughputs and network capacity, reducinglatency, and increasing mobility.

User equipment devices obtain access to the E-UTRAN via a wirelessnetwork access device referred to as an evolved Node B (i.e., eNB oreNB) that is described in more detail with reference to FIG. 1. In amobile communication network, the eNB is a hardware device that providesa wireless radio communication interface that facilitates thecommunication between a user's mobile device and other nodes or elementsforming the mobile communication network. An eNB communicates with a UEover an air interface and communicates (both voice over IP (i.e., voiceover LTE (VoLTE)) and data) with other network devices to send andreceive information to the UE and other users or entities (e.g.,websites or applications). An eNB may include one or more wirelesstransceivers that receive digitized voice and/or data from a radionetwork controller and transmit that voice and/or data to UE via adownlink of the air interface. One or more wireless transceivers of theeNB also receive digitized voice and/or data from the UE via an uplinkof the air interface and transmit that voice and/or data via the radionetwork controller to/through other elements or nodes of the network,e.g. to other UE devices and/or to websites or other applicationservers.

The owner of an HeNB subscribes to a specific cellular communicationservice provider, or mobile network operator for the provision ofcellular service to the HeNB. The HeNB connects to broadband Internetaccess network at the premises where the owner intends to use thedevice, e.g. to a cable modem service or to a fiber-to-the-home typeInternet service provider network. To a mobile device, however, the HeNBappears the same as a macro eNB of the broader area public cellular LTEnetwork. A typical use of an HeNB is for providing cellular coveragewithin an office building or to an area with poor cellular coverage thatalso has low traffic (i.e., a modest number of UE moving in and out tothe femtocell).

A UE, such as UE 180, in the area of an HeNB can attach to the cellularcommunication network via the HeNB and obtain cellular service (i.e.,voice and data communications). When an HeNB connects to a mobilecommunication network, the mobile communication network begins trackingany UE that connects to the HeNB. An HeNB can be implemented whereveraccess to the Internet or similar type of network that allowsconnectivity to servers of a cellular communication service provider isavailable. Once the HeNB is connected to Internet access service, the UEcan begin detecting reference signals from the HeNB within a coveragearea of an eNB. As a result, the UE begins reporting the presence of theHeNB as a potential connection point to entities within the mobilecommunication network.

The various examples disclosed herein relate to facilitating a handoverof control of a user equipment (UE) device of a user moving from an eNBcoverage area to a neighboring HeNB coverage area. The followingprovides examples for minimize the burden on the network devices tomanage the administration of TAIs. The examples utilize alternateinformation provided according to the 3GPP standards to facilitate thehandover of control without having to rely upon a TAI of a eNB or HeNB.Reference now is made in detail to the examples illustrated in theaccompanying drawings and discussed below.

FIG. 1 is a diagram of an example environment 100 in which systemsand/or methods described herein may be implemented. As shown in FIG. 1,environment 100 may include a mobile device or UE 180, a long termevolution (LTE) type radio access networks (RAN) 111, an evolved packetcore (EPC) network 131, a network 170, such as the Internet, and anInternet protocol (IP) multimedia subsystem (IMS) core network 190.Communications of any form between the respective network elements 111,131, 170 and 190 are illustrated by the arrows labeled COMM, and cantake the form of wired or wireless communications.

The LTE RAN 111, for example, is a radio access network (RAN) thatincludes a number of network components that provide packet datatransport services to user equipment (UE), such as UE 180. For example,the LTE RAN 111 includes one or more devices for transmitting voiceand/or data to UE 180 and to EPC network 131 and core network 190. Inone example implementation, the LTE RAN 111 includes a group of basestations 113, 117 implemented as eNBs and HeNBs, respectively. In oneexample, the LTE RAN 111 provides a wireless access network for UE 180.In another example, the LTE RAN 111 includes a WiFi network or otheraccess networks (e.g., an enhanced high-rate packet data (eHRPD) networkor a WiMax network). In the current LTE example, the LTE RAN 111utilizes packet switching. For convenience, switches and/or routers forhandling the flow of packets through the LTE RAN 111 are omitted.

Signaling between the LTE RAN 111 and the EPC Network 131 is performedaccording to different protocols. One such protocol is an S1 interfaceprotocol. The S1 interface represents the interface between therespective eNBs in the network and the EPC network. The S1 interface hastwo different interfaces: the S1-MME interface for exchanging controlsignals (eNB and MME, HeNB GW and MME, and (in other implementations)HeNB and MME) and the S1-U interface for exchanging voice and datacommunications. In an example, the S1-MME interface for exchangingcontrol signals exists between eNB 113 and MME 137; HeNB GW 115 and MME137; and an individualized HeNB (not shown in FIG. 1, but see, forexample, HeNB 347 of FIG. 3B) and MME. In other examples, the S1-MMEinterface is implemented only between the eNB and the MME; and the HeNBGW and the MME. In an example, the S1-U interface for exchanging controlsignals exists between the eNB and SGW 135, HeNB GW and SGW 135 and anindividualized HeNB (not shown in FIG. 1, but see, for example, HeNB 347of FIG. 3B) and SGW 135. The S1 interface protocol communications areillustrated by the COMM arrow between the LTE RAN 111 and the EPC 131.

The EPC 131 is provided by the cellular communication service provider(i.e., a mobile communication network operator (MNO)) and facilitatesthe exchange of data packets containing voice and data communications.In an example, the LTE RAN 111, the EPC network 131 and the IMS core 190are provided by a cellular communication provider (i.e., MNO). An EPCnetwork may include nodes and functions that provide Internet Protocol(IP) connectivity to and from one or more LTE RAN 111 and the UE 180,for data, voice, and multimedia services. The EPC network 131 utilizespacket switching for packet transport, although for convenience,switches and/or routers for handling the flow of packets through the EPCnetwork 131 are omitted. When a UE registers with the EPC network 131through an attach procedure, information about the UE 180 is stored in aMME device 137. Thus, a MME device 137 in the EPC network 131 includes adatabase that stores information about UEs including UE 180.

As shown in FIG. 1, EPC network 131 connects UE 180 to one or moreexternal IP networks 170. The EPC network 131 may connect to othernetworks, such as the public switched telephone networks, although suchother connections are omitted for ease of illustration. The EPC network131 typically include one or more devices that implement logicalentities interconnected via standardized interfaces, and that providewireless packet-switched services and wireless IP connectivity throughthe LTE RAN 111 to UE 180 for both data and voice services. The EPCnetwork 131 may allow the delivery of broadband IP services and mayinterface with external IP network 170 (e.g., an IMS network) forapplication services offered or controlled by the carrier or otherservice provider operating the overall mobile service network (includingnetworks 111 and 131). In some examples, the cellular service providenetwork, or mobile communication network, includes the LTE RAN 111, theEPC network 131 and the IMS core 190. Of course, components of each of111, 131 and 190 may be incorporated into the other to omit or augmentfunctionality in one network or another.

The UE 180 may take the form of any communication device that a user mayuse to connect to EPC network 131 through the LTE RAN 111 and in somecases through other wireless access networks (and/or intermediatenetworks).

The eNB 113 may include one or more devices (e.g., processors andtransceivers) and other components and functionality that allow UE 180to wirelessly connect to EPC network 100. The eNB 113, for example, is amacro-scale base station and provides cellular communication service toa macrocell coverage area. The eNB 113 interfaces with EPC network 131via the S1 interface protocol, which may be split into a control planeS1-MME interface (not shown) and a data plane S1-U interface (notshown). The S1-MME interface interfaces the control functionality withinthe eNB with MME device 137 in the EPC network 131, by defining themessages and contents thereof exchanged between the controlfunctionality within the eNB and the MME device 137. The S1-MMEinterface may be implemented, for example, with a protocol stack thatincludes a Non Access Stratum (NAS) protocol and/or Stream ControlTransmission Protocol (SCTP). The S1-U interface interfaces the controlfunctionality within the eNB with serving gateway (SGW) 135, by definingthe messages and contents thereof exchanged between the controlfunctionality within the eNB and the SGW 135; and the S1-U interface isimplemented, for example, using a General Packet Radio Service TunnelingProtocol version 2 (GTPv2).

The HeNB 117 is a base station that provides substantially the samefunctionality as the eNB, but on a smaller scale. For example, the HeNB117 is a portable device and includes a processor, a wirelesstransceiver for accessing LTE RAN 111, and components for formingconnections to the internet via other wired or wireless networks (e.g.,WiFi, fiber optic or the like). In the examples, the HeNB 117 isconsidered a small-scale base station that provides a small-scale cell,or femtocell, coverage area. The connection between the femtocellmanagement controller 133 and the HeNB 117 is a connection, such as forexample, a fiber optic or coaxial, a microwave, or satellite connection,and may traverse one or more networks. Communications of any formbetween the femtocell management controller 133 and the HeNB 117, and/orthe HeNB-GW 115 are illustrated by the connections between the elements,and can take the form of wired or wireless communications. The HeNB-GW115, for example, is similarly connected to the HeNB 117 and any otherHeNB 117 managed by the HeNB-GW 115. From the perspective of the HeNB117, the HeNB-GW 115 appears to as an eNB, such as eNB 113. The HeNBs inthe environment 100, such as HeNB 117, are managed by a femtocellmanagement controller 133, which is part of the LTE RAN 111. Thefemtocell management controller 133, for example, at time ofinitialization establishes a secure connection (e.g., based on exchangeof authentication credentials and/or other subscriber-relatedinformation) between the HeNB, such as HeNB 117, and mobilecommunication provider servers (not shown) in the EPC 131. The femtocellmanagement controller 133 has access to pre-configuration informationfor any HeNBs that will be joining the mobile communication network ofthe environment 100. During process for the provisioning the HeNB withthe mobile communication network, the HeNB will provide locationinformation (such as global positioning system (GPS) information) to thefemtocell management controller 133. Based on the location information,a TAI is assigned to the HeNB by the femtocell management controller133. Using the pre-configuration information, the femtocell managementcontroller 133 begins to provision the HeNB with preconfigure settingsbased on the location (i.e., TAI) of the HeNB to obtain from or providethe HeNB with the information and settings needed for the HeNB to beoperational within the mobile communication network. This type ofimplementation, for example, allows for a more rapid provisioning of theHeNB into the mobile communication network as compared to an eNB setupand provisioning.

The MME device 137 implements, among other functions, control planeprocessing for EPC network 131 for management of mobility of UE devicessuch as 180 roaming amongst cellular service areas covered by one ormore LTE RAN 111. The MME 137 communicates with the eNB 113 and theHeNB-GW 115. For example, MME device 137 via communications with therespective eNB 113 and the HeNB-GW 115 implements tracking and pagingprocedures for UE 180, activates and deactivates bearers throughnetworks 111, 131 for UE 180, authenticates a user of UE 180, and mayinterface to non-LTE RAN. The MME device 137 also selects a particularSGW 135 to service a communication session for a particular UE 180.

In some examples, the MME device 137 (i.e., a network device) managesmultiple base stations, such as eNB 113 in LTE RAN 111. The MME 137sends and receives information associated with mobile devices, such asUE 180. For example, the eNB 113 may be a servicing, or source basestation that provides cellular communications to the mobile device UE180. However, as the mobile device UE 180 travels better qualitycellular communications may be provided by the HeNB 117. As a result,the eNB 113 may determine to allow the target base station device, ortarget HeNB 117, to take over control of communication services for themobile device UE 180. After handover of control, the MME device 137continues to provide control plane processing for mobile devicesserviced by the target base station device, such as HeNB 117, when theUE 180 travels away from the eNB 113.

For example, the MME device 137 may communicate with SGW 135. The MMEvia the S11 interface creates and manages a new session for a particularUE 180. The S11 interface is activated when MME device 137 needs tocommunicate with SGW 135, such as when the particular UE 110 attaches toEPC network 131, when bearers need to be added or modified for anexisting session for the particular UE 180, when a connection to a newpacket data network (PDN) gateway (PGW) 139 needs to be created, orduring a handover procedure (e.g., when the particular UE 110 needs toswitch to a different SGW 135). While the control functions are managedby the MME 137, the actual delivery of the data communications ishandled by the SGW 135 of the EPC 131. For example, the SGW 135 providesdata pathway to and from UE 180, may handle forwarding of data packetsfor UE 110, and acts as a local anchor point during handover proceduresbetween eNBs 113 as well as handover procedures between the eNBs 113 andany HeNBs 117 via the HeNB gateway (HeNB-GW) 115.

The HeNB-GW 115 manages the data communication signals and the controlplane signals exchanged between the MME 137 and the HeNB 117. From theperspective of the MME 137, the HeNB-GW 115 appears to be an eNB, suchas eNB 113. The HeNB-GW 115 is configured to include a processor andmemory and connects to the respective HeNBs under its control the LTEradio access network 111. The HeNB-GW 115 acts as a gateway for signalsfrom the MME 137 to the HeNBs managed by the HeNB-GW 115. The HeNB-GW115 will be described in more detail with reference to examples of FIGS.2-6. The HeNB-GW 115 is configured to handle multiple HeNBs, but onlyone HeNB 117 is shown for ease of explanation.

The IMS core network 190 includes HSS/AAA server 192 and/or CSCF server194. The MME 137 communicates with the HSS/AAA server 192 and/or CSCFserver 194 when a mobile device, such as mobile device UE 180 isattempting to attach to the mobile communication network (i.e., the LTEradio access network, the EPC 131 and the IMS core network 190). TheHSS/AAA server 192 and CSCF 194 provide or assist with theauthentication, session initiation, account information, profileinformation, and the like associated with mobile device UE 180. Ofcourse, the IMS core network 190 may include additional components toprovide functionality associated with the UE 180.

Network 170 may include one or more wired and/or wireless networks. Forexample, network 170 may include a cellular network, a public landmobile network (PLMN), a second generation (2G) network, a thirdgeneration (3G) network, a fourth generation (4G) network, a fifthgeneration (5G) network, and/or another network. Additionally, oralternatively, network 170 may include a wide area network (WAN), ametropolitan network (MAN), an ad hoc network, an intranet, theInternet, a fiber optic-based network, and/or a combination of these orother types of networks. Additionally, or alternatively, network 170 mayinclude, or connect to, an external IP network. The external IP networkmay include, for example, another IMS network, which may provide voiceand multimedia services to user device 180, based on the SessionInitiation Protocol (SIP). Herein, a cellular network may refer to aportion of environment 100 and/or one or more other networks.

Although FIG. 1 shows example devices/networks of environment 100, inother implementations, environment 100 may include fewerdevices/networks, different devices/networks, differently arrangeddevices/networks, and/or additional devices/networks than depicted inFIG. 1. Alternatively, or additionally, one or more devices ofenvironment 100 may perform one or more tasks described as beingperformed by one or more other devices of environment 100.

FIG. 2 illustrates an example allocation of tracking area identifiersaccording to the described subject matter. In the cellular networkenvironment 200 of FIG. 2, the cellular coverage area, or macrocell 225,is serviced by a macro-scale base station, such as eNB 230. The cellularnetwork environment 200 includes user equipment devices 288 and 180.Both UE 288 and 180 obtain cellular voice and data communications fromthe eNB 230. The eNB 230 communicates with an MME 247 of the cellularcommunication network. The MME 247 manages the provision of cellularvoice and data communications and control services to the UE 288 and180. Based on the physical location of the eNB 230, a tracking areaidentifier (TAI) is assigned to the eNB 230. The MME 247 maintains alisting of TAIs and the eNBs assigned the respective TAIs. More than oneeNB may be assigned the same the TAI. In the illustrated example, theTAI assigned to eNB 230 is TAI-1. The TAI assigned to the eNB 230 isalso sent to the eNB 230 for distribution to all UE devices within rangeof the eNB 230. For example, UEs 288 and 180 are provided with the eNB230 TAI of TAI-1. Each mobile device, such as UE 288 and 180, maintain alist of base stations, such as eNB 230, that are detected by therespective mobile devices. On occasion, or periodically, the respectiveUE 288 or 180, for example, in response to instructions from the MME247, surveys the environment to detect base stations, such as eNB 230,that are transmitting reference signals. Upon receipt of the referencesignals, the UE 288 and 180 may analyze the reference signals from therespective base stations. For example, the UE 288 and 180 may determinea received signal strength (RSS) indicating how close the UE is to oneor more base stations, or how unobstructed the respective base stationsignals are in comparison to other base station signals. Of course,reference signals of base stations from macrocells (not shown) otherthan macrocell 225 may also be detected and analyzed. The results of theanalysis are reported to the MME 247.

As discussed above, HeNBs, such as HeNB 235, are able to be added to thecellular communication network at almost any location that providesaccess to the Internet, such as networks 170 of FIG. 1. Uponestablishing the Internet connection and exchanging provisioninginformation with the MME 247 of the cellular communication networkprovider, the HeNB 235 is configured to begin providing cellular servicein a small coverage area shown as femtocell 250. An HeNB managementelement, such as femtocell management controller 133 in FIG. 1, assignsthe HeNB 235 to an HeNB-GW, such as HeNB-GW 249, for managing control ofthe HeNB 235. A purpose of an HeNB-GW is to aggregate the control planetraffic of multiple HeNBs, such as HeNB 235, connected directly to theHeNBs and to interact with the MME 247 in the same manner as a singleeNB. In such a case, the HeNB 235 provides substantially the samefunctionality and has substantially the same capabilities as the eNB 230except on a smaller scale and with limited range (i.e., limited coveragearea as compared to eNB 230). In other words, the HeNB 235 is asmall-scale base station, which has a limited coverage area, such asapproximately one square city block, approximately two acres,approximately 35-500 feet radius from HeNB antenna or the like. Thefemtocell 250 coverage area provided by the HeNB 235, in the example,arises within the macrocell 225 serviced by eNB 230. UE in the area ofthe femtocell 250 are able to receive cellular data and voicecommunication service from the HeNB 235, and may also be able to obtainservice from eNB 230. For example, an example of limited range may be anenterprise campus that includes four buildings arranged in a square thatcovers several acres in which a single HeNB in the center of the squareprovides service to the enterprise's employees in each of the fourbuildings.

In order to account for the presence of the HeNB 235, the cellularservice provider preconfigures the HeNB management system with the TAIallocations, and, during the provisioning of the HeNB 235 with thenetwork, the appropriate TAI is assigned to the HeNB 235. However, thenumber of TAIs available for assignment to HeNBs under control ofHeNB-GWs is limited to those TAIs dedicated for assignment to anHeNB-GW. Recall that only a limited number of dedicated TAIs, asexplained above, are available for assignment. In the example of FIG. 2,TAI-2 has been assigned to the HeNB 235. Other HeNBs 239 may also be inthe area and have been assigned TAIs different from TAI-2. In differentimplementations, several of the other HeNBs may be assigned the sameTAI. For example, femtocells 251 and 252 and the respective HeNBs 238and 238 share the same TAI (i.e., TAI-3) due their respectivegeographical location of the HeNB. In some examples, a HeNB-GW maymanage a number of HeNBs associated with a large enterprise, such as amanufacturing facility or college campus, in which the capabilities(e.g., range, bandwidth capabilities and the like) of all of the HeNBsare the same. In other examples, a HeNB-GW may manage a number of HeNBsthat have different capabilities, such as one HeNB may have short rangeand limited bandwidth, while another HeNB managed by the same HeNB-GWmay have a longer range and a greater bandwidth.

The UE 180 and UE 288 are constantly monitoring their environment, forexample, by detecting signal differences between signals received fromone base station and those received from another base station. Forexample, the UE 180 may determine the RSS of signals from a respectivebase station as mentioned above. Based on the determined RSS, forexample, the UE 180 may determine that one base station is providing ahigher quality signal than another base station.

For example, the UE 180 sends the signal measurement information to theserving eNB, for example, eNB 230. The serving eNB 230 receives thesignal measurement information from the UE 180, and based on the signalmeasurement information determines that another base station 235 infemtocell 250 is better suited for providing optimum service to the UE180. The MME 247 uses the information reported by the respective UEsunder control of the MME to perform the UE's access control and toassist with the message flow between base stations included in thereported information that would provide optimum service to the UE. Forexample, the UE 180 may be receiving a signal with a much higher RSSfrom the HeNB 235 than signals received from the eNB 230. Based on thisinformation regarding the much higher RSS from the HeNB 235, the eNB 230and the MME 247 determine that the providing of voice and datacommunication service to the UE 180 should be handed over from the eNB230 to the HeNB 235. This process referred to as a “handover” isillustrated in more detail in FIG. 3A.

FIG. 3A is a process diagram showing an example of a mobile devicehandover request according to an example of the described subjectmatter. The network environment 300 of FIG. 3B includes a source eNB325, a target HeNB 350, a UE 380, an HeNB-GW 345, and a MME 340. The MME340, for example, includes a communication interface configured to sendand receive signaling communications via a mobile wireless communicationnetwork, a memory that stores, for example, handover routinginformation, and a processor coupled to the interface and the memory.

In the example of FIG. 3A, the source eNB 325 is the base station thatis providing service to the UE 380. The MME 340 may also include aninterface with a small-scale base station gateway, such as HeNB-GW 345.The structural details of an MME, such as MME 340, are described in moredetail with reference to FIG. 5. The MME 340 processor is alsoconfigured to transmit control signals to the mobile device to performfunctions related to mobility management and other network-relatedfunctions. The functions are described in more detail with reference tothe steps illustrated in FIG. 3A.

As mentioned above with respect to FIG. 2, the UE 380 triggers one ofthe conditions for a TAU. This is shown as step 1 in FIG. 3A. As part ofthe TAU, the UE 380 detects reference signals from base stations in thevicinity of the UE 380. For example, the UE 380 may be provided, forexample, by an eNB servicing the UE 380 or the like, with a list of basestations that are servicing neighboring cells (macro-scale cells andsmall-scale cells). The list includes frequency information related tothe signals transmitted by each base station so the UE may tune to theappropriate frequency to detect reference signals from the respectivebase stations in the list. The overhead messages from the respectivebase stations include information that identifies the respective basestation transmitting the reference signal.

As background, each base station has information that is used bydifferent components of the mobile communication network to identify ormonitor network utilization and/or performance. For example, the targeteNB 350 provides signals to the UE 380 that include an enhanced cellglobal identifier (ECGI), and a TAI (both of which will be described inmore detail below). In addition, the respective base station may includea closed subscriber group (CSG) identity (CSGI). A CSG is a group ofusers that have access to the particular HeNB, such as HeNB 350. Thegroup of users that may have access the HeNB and are able to receivevoice and data communication service via the femtocell are included in alist stored in the HeNB 350. For example, identifiers of the respectiveUEs of the users in the allowed group may be stored in the list. The CSGis determined when the HeNB 350 is configured. Alternatively, the HeNB350 may be configured as having open access in which case any user isable to access the HeNB 350 and obtain voice and data communicationservice via the femtocell.

Each of these identifiers (i.e., ECGI, TAI and/or CSGI) providesdifferent information to the source eNB 325 and the MME 340 about thetarget eNB 350. Some of the identifiers may be concatenations of otheridentifiers. For example, the PLMN ID is an identifier that identifiesthe network in which the target base station is connected. The PLMN IDis a combination of two other identifiers: a mobile country code (MCC)and a mobile network code (MNC). The MCC identifies the home country(e.g., USA) of the UE subscriber and the MNC identifies the networkwithin the MCC.

For example, the HeNB 350 provides its assigned ECGI identifier to theUE 380. The ECGI is an identifier that uniquely identifies a cell, whichis a geographical area, serviced by a base station in the mobilecommunication network. The cell may be referred to as a macrocell (i.e.,a macro-scale cell), which is serviced by an eNB or a femtocell (i.e., asmall-scale cell), which is serviced by a HeNB. Recall that the targetHeNB 350 provides the ECGI and the TAI of the target HeNB 350 to the UE380 in the reference signals transmitted by the HeNB 350. The targetHeNB 350 ECGI is a concatenation of different types of identifiers. Inthis example, the target HeNB 350 ECGI uniquely identifies the HeNB 350and includes a PLMN ID and an E-UTRAN identifier (ECI). The ECI has 20bits of eNB ID and 8 bits of Cell identifier (ID). In some examples, theHeNB-GW 345 is identified by using an eNB ID and the MME can use the eNBID to identify the HeNB-GW 345 in the mobile communication network. The8-bit Cell ID in the ECI is used to identify HeNBs connected to theHeNB-GW 345. For example, multiple ECIs may be assigned to an HeNB-GW345, the 20 bits of the eNB ID may be used to identify the HeNB-GW 345and the 8 bits of the Cell ID are used to identify individual HeNBsconnected to the HeNB-GW 345, such as HeNBs 353-357. The use of the ECGIby the MME 340 will be discussed in more detail below.

Returning to step 3 of the example of FIG. 3A, the UE 380 reports theinformation included in the respective reference signals of the detectedbase stations such as a ECGI, TAI, PLMN IDs and the CSGI of therespective bases stations detected by the UE 380 to the source eNB 325.The UE 380 may also report measurements performed by the UE 380, such asRSS, related to the received reference signals to the source eNB 325(shown as Step 2). The source eNB 325 sends the information to MME 340.The information send to the MME 340 by the source eNB 325 includes thevarious identifiers, target cell ECGI, PLMN ID, CSG information, ifrelevant, and any similar information of other eNBs or HeNBs detected bythe UE 380 to the source eNB 325. The information sent to the MME 340also includes identifying information of the source eNB 325. The sourceeNB 325 may with or without the cooperation of the MME 340 determinethat service to the UE 380 should be handed over to the target HeNB 350from the source eNB 325. For example, based on the information, thesource eNB 325 and the MME 340 determines that a handover from thesource eNB 325 to another base station, in this case, target HeNB 350 isappropriate. The handover determination may be made based on one or morefactors, such as the networks utilization of resources, the measuredsignal quality of the other base stations in comparison to the measuredsignal quality of the source eNB 325, and the like. In the example, thetarget HeNB 350 may be determined to be the optimum (e.g., based onsignal quality and network utilization) base station for deliveringvoice and data communication to the UE 380. In response to the sourceeNB 325 making the handover determination, the source eNB 325 generatesa handover request that is forwarded to the MME 340 (step 4). Thehandover request sent to the MME 340. The information in the handoverrequest, for example, includes information, such as the variousidentifiers, target cell ECGI, PLMN ID, CSG information, specific to thetarget HeNB 340, which the optimum base station to provide service tothe UE 380.

The MME 340 has to route the UE 380 information to the base stationidentified in the handover request information. In order to determinehow to route the information, the MME 340 may use different techniquesto determine the identity of the target HeNB. The different techniquesmay be better explained with reference to FIG. 3B. The mobilecommunication environment 301 of FIG. 3B includes the MME 340 which isconnected to a number of base stations, eNB(s) 343, HeNB(s) 347 and anHeNB-GW 345. The communication between the MME 340 and the eNB(s) 343,HeNB(s) 347 and an HeNB-GW 345 is via a communication protocol referredto as the S1-MME interface. The eNBs 343 are macro-scale base stations,each of which is assigned a TAI. In some examples, multiple eNBs 343 mayshare the same TAI. The directly connected HeNBs 347 are also assignedTAIs similar to the macro-scale base stations, such as eNB 343. Althoughthe HeNB(s) 347 are considered small-scale base stations similar toHeNBs 353 and 357, the HeNB(s) 347 are not assigned TAIs from the poolof dedicated TAIs because the HeNB(s) 347 are directly connected to, or,in other words, managed by, the MME 340 without reliance on a HeNB-GW.The HeNB-GW 345, as mentioned above, manages operation of several HeNBs,such as HeNB 353-357. The HeNB-GW 345, in some examples, has a singleTAI assigned to it. This single TAI is assigned from the pool of TAIsdedicated for assignment to HeNBs. Note that all of the TAI assignmentsand other information needed or managed by the MME 340 may be stored ina database 423 accessible to the MME 340.

In the above example, when a single TAI is assigned to the HeNB-GW 345,each of the HeNBs 353-357 are grouped within that TAI. Alternatively, inother examples, the HeNB-GW 345 has more than one TAI assigned to it.Each of the more than one TAI may have one or more of the HeNBs 353-357grouped in the respective TAI. For example, TAI-XX and TAI-YY areassigned to the HeNB-GW 345, and HeNB 353 may be assigned to TAI-XX andHeNBs 354-357 may be assigned to TAI YY. The assignment of the HeNB to aparticular TAI may be based on a number of predetermined factors, suchas distance of the HeNB location to a center point of the area coveredby the TAI, a number of HeNBs already assigned to a TAI, balancing thenumber of HeNBs assigned to the pool of TAIs (i.e., attempt to evenlyspread the assignment of HeNBs among the TAIs in the TAI pool), or thelike. The MME 340, when operating in a network environment, such as 301that permits a MME to be directly coupled to an HeNB, such as HeNB(s)347, is able to use the TAI assigned to the target HeNB to locate thetarget HeNB for delivery of the handover information. Alternatively, ifthe target HeNB is managed by HeNB-GW 345, the MME 340 needs only tolocate the HeNB-GW 345 because the HeNB-GW 345 is able to use thehandover information to locate the target HeNB, which HeNB-GW 345 ismanaging.

For example, network device, such as MME 340, includes a communicationinterface, a memory and a processor. The hardware details of the networkdevice, such as MME 340 are discussed in further detail with referenceto FIG. 5. The communication interface is configured to send and receivesignaling communications via a mobile wireless communication network.The memory storing handover routing information in a routing list, alist of target base stations connections within the mobile wirelesscommunication network, and program instructions. The processor iscoupled to the interface and the memory. The processor of the MME 340may execute logic embodied in program instructions stored in memory.

In an example, the MME 340 receives handover requests from respectivemobile devices via the mobile wireless communication network and acommunication interface. Each handover request, for example, isrequesting handover of the respective mobile device from a macro-scalebase station of the mobile wireless communication network to a targetbase station identified by an enhanced cell global identifier includedin handover information contained in the handover request. The executedlogic in response to each respective one of at least a plurality of thehandover requests, determines from the enhanced cell global identifierin each respective handover request that the target base stationidentified in the respective handover request is a small-scale basestation. The logic further in response to each determination of anidentified target base station as being a small-scale base station,compares the enhanced cell global identity of the identified target basestation with a list of target cells not directly connected to thenetwork device providing control services to the respective mobiledevice. In response to a result of the comparison indicating a negativematch result, the processor executing the logic further compares theenhanced cell global identity of the identified target base station witha routing list of target base stations directly connected to the networkdevice providing the control services to the respective mobile device.In this example, the handover request message is routed to theidentified target base station in response to a result of the furthercomparison indicating a positive match.

Continuing with the example, in response to the initial comparisonresult indicating that the identified target base station is in the listof target base stations not directly connected to the network device,the handover request is routed to another network device for ultimaterouting to a network device that provides control service to the UE.Alternatively, a message may be returned to the UE that a handover tothe target base station is not permitted. In response, the UE may eitherrequest a handover to another target base station or may choose toremain under control of the network device providing control services.Similarly, in response to the further comparison providing a negativeresult, the handover request is routed to another network device forultimate routing to a network device that provides control service tothe UE. Alternatively, a message may be returned to the UE that ahandover to the target base station is not permitted.

As discussed above, the dedicated pool of TAIs is required forassignment to HeNB-GWs so that the MME can correctly route messagesbased on the assigned TAI. In addition, since the TAIs in the pool arededicated for assignment to the HeNB-GWs in the mobile communicationnetwork, the TAIs in the dedicated pool cannot be used for assignment tothe macro-scale eNBs. In some implementations, a HeNB-GW, such asHeNB-GW 345, has multiple TAIs assigned to it from the dedicated pool ofTAIs. Once the message is directed to the correct HeNB-GW, then theHeNB-GW routes the message to the correct HeNB based on the otheridentifiers included in or with the message. However, to reduce the useof the TAI and therefore, reduce the need to have a dedicated pool ofTAIs, other techniques that do not rely on the TAI may be used. Inanother example, the MME 340 may be configured in to rely on the ECGI,which, as discussed above, is a concatenation of a PLMN ID, an eNBidentifier, and a cell identifier.

To explain the use of ECGI in more detail reference is made to FIG. 4,which shows a networking environment 400 that includes an MME 440coupled to a HeNB-GW 445. Each HeNB-GW in the network environment, suchas HeNB-GW 445, is able to manage 256 HeNBs, such as HeNBs 451-455.Although the HeNB-GW 445 is not an eNB, the MME 440 assigns an eNBidentifier to the HeNB-GW 445. The HeNB-GW 445 is able to generate itsown ECGI group based on the eNB identifier. As such, each of the HeNBs451-455 managed by the HeNB-GW 445 is assigned one of the 8-bit cellidentifiers included in an ECGI. In other words, the HeNB-GW 445 is ableto assign an 8 bit identifier (i.e., a Cell identifier (ID) in the ECGI)to the target HeNB 340 that is used by the HeNB-GW 445 to uniquelyidentify the target HeNB 340. The 8-bit Cell ID is concatenated to theeNB ID to create the ECGI of the respective HeNBs 451-455. In anexample, all of the HeNBs 451-455 connected to the HeNB GW 445 share thesame HeNB ID that is assigned to the HeNB-GW 445, but each HeNB isuniquely identifiable by the 8 bits of the Cell ID.

For example, referring back to FIG. 3B, the MME 340 has created ECGIgroups that are stored in memory 323. A first ECGI group may includemacro-cell eNBs 343 and directly connected HeNBs 347, and a second ECGIgroup may include the ECGI of HeNB-GW 345. One of the HeNBs 353-357 isthe target HeNB selected for handover from the source eNB. Returning tothe example of FIG. 3A, the MME 340 by applying the ECGI techniquesdiscussed above, to the handover information (i.e., the target HeNB TAI,ECGI and CSG information) passed by the source eNB 325 (at step 4), theMME 340 is able to identify the HeNB-GW 345 as the device that ismanaging the target HeNB 340. At step 5 of FIG. 3A, the MME 340 deliversthe handover request information to the HeNB 345 in preparation forhanding over service from the source eNB 325 to the target HeNB 345.

After receiving the handover information from the MME 340, the HeNB-GW345, which is, in this example, an intermediary device, determines theidentity of the target HeNB 340 by a process explained with reference toFIG. 4. As shown in FIG. 4, the HeNB-GW 445 has an ECGI equal to123456xx. In other words, the MME 440 uses, for example, only the first6 digits of the ECGI to determine that the ECGI is assigned to theHeNB-GW 445 as opposed to any other eNBs or directly connected HeNBs.For example, the MME 440 may access a routing list or other databasestructure that lists ECGIs of the respective HeNB-GWs and compare theECGI to ECGIs in the routing list. The routing list may be for theentire mobile communication network or specific to the devices managedby the MME 440. After determining the ECGI is specific to the HeNB-GW445, the MME 440 passes the handover information to the HeNB-GW 445. Inresponse to receiving the handover information, a processor in theHeNB-GW 445 analyzes the entire ECGI or only the cell id (last 8 bits)of the ECGI to determine the identity of the target HeNB in the group ofHeNBs 451-455. Upon identifying the target HeNB, the HeNB-GW 445 sendsthe handover information to the identified target HeNB.

An advantage of the described examples is that the dependency on adedicated list of TAIs for the HeNBs is no longer required and theoperators can set the same TAI for a HeNB as the TAI assigned to theoverlaying eNB. These features make the TAI planning simpler and reduceunnecessary overhead signaling and “ping-pong” scenarios of TAUprocedure triggering as the UE skirts (i.e., moves in and outof—ping-pongs) the border areas between an HeNB and an eNB.

FIG. 5 is a simplified functional block diagram of a computer that maybe configured as a network device, such as a mobility management entityor a HeNB gateway according to an example of the described subjectmatter.

A server or controller, for example, includes a data communicationinterface for packet data communication. The server, controller ordevice, such as a base station (e.g. eNB) or a cellular network mobilitymanagement entity (e.g. MME), also includes a central processing unit(CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.In addition, to the communication ports for exchanging communicationswith a network, the server or controller may be equipped with a wirelesscommunications transceiver to communicate with devices, such as the basestation (e.g. eNB) or the cellular network mobility management entity(e.g. MME). In addition, such a wireless network base station orcellular network MME includes one or more wireless transceivers in orderto provide communications services to one or more mobile devices (e.g.,UE) via various radio frequencies in compliance with one or morewireless communications standards (e.g., LTE). The hardware elements,operating systems and programming languages of such servers areconventional in nature. Of course, the server functions may beimplemented in a distributed fashion on a number of similar platforms,to distribute the processing load.

At least some aspects of the method for effecting efficient handover ofUE service and control without or with limited use of a TA as outlinedabove may be embodied in programming, e.g. for the mobile device, theconnectable device, and/or the provisioning system server. Programaspects of the technology may be thought of as “products” or “articlesof manufacture” typically in the form of executable code and/orassociated data that is carried on or embodied in a type of machinereadable medium. “Storage” type media include any or all of the tangiblememory of the computers, processors or the like, or associated modulesthereof, such as various semiconductor memories, tape drives, diskdrives and the like, which may provide non-transitory storage at anytime for the software programming. All or portions of the software mayat times be communicated through the Internet or various othertelecommunication networks. Such communications, for example, may enableloading of the software from one computer or processor into another, forexample, from a management server or host computer of the provisioningsystem into the computer platform of a user mobile device or aconnectable device. Thus, another type of media that may bear thesoftware elements includes optical, electrical and electromagneticwaves, such as used across physical interfaces between local devices,through wired and optical landline networks and over various air-links.The physical elements that carry such waves, such as wired or wirelesslinks, optical links or the like, also may be considered as mediabearing the software. As used herein, unless restricted tonon-transitory, tangible “storage” media, terms such as computer ormachine “readable medium” refer to any medium that participates inproviding instructions to a processor for execution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement theconnectable device provisioning service, etc. shown in the drawings.Volatile storage media include dynamic memory, such as main memory ofsuch a computer platform. Tangible transmission media include coaxialcables; copper wire and fiber optics, including the wires that comprisea bus within a computer system. Carrier-wave transmission media can takethe form of electric or electromagnetic signals, or acoustic or lightwaves such as those generated during radio frequency (RF) and infrared(IR) data communications. Common forms of computer-readable mediatherefore include for example: a floppy disk, a flexible disk, harddisk, magnetic tape, any other magnetic medium, a CD-ROM, DVD orDVD-ROM, any other optical medium, punch cards paper tape, any otherphysical storage medium with patterns of holes, a RAM, a PROM and EPROM,a FLASH-EPROM, any other memory chip or cartridge, a carrier wavetransporting data or instructions, cables or links transporting such acarrier wave, or any other medium from which a computer or the like canread programming code and/or data. Many of these forms of computerreadable media may be involved in carrying one or more sequences of oneor more instructions to a processor for execution.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

The scope of protection is limited solely by the claims that now follow.That scope is intended and should be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 180, or 103 of the Patent Act, nor should they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A first device, comprising: one or moreprocessors to: receive a request for a handover of a mobile device froma first base station to a second base station, the first base stationbeing a macro-scale base station, and the request including handoverinformation, the handover information including an identifier, theidentifier being a type of identifier used to identify at leastmacro-scale base stations and small-scale base station gateways,  amacro-scale base station, of the macro-scale base stations, providingcellular communication service to a macrocell coverage area; determinethat the second base station is a small-scale base station based on theidentifier identifying a particular small-scale base station gateway,the small-scale base station providing a small-scale cell coverage area;determine, based on the identifier and based on determining that thesecond base station is the small-scale base station, that the secondbase station is connected to the particular small-scale base stationgateway, one or more small-scale base stations, including the secondbase station, being managed by the particular small-scale base stationgateway, and the particular small-scale base station gateway and thefirst base station being managed by the device; and provide the handoverinformation to the particular small-scale base station gateway based ondetermining that the second base station is connected to the particularsmall-scale base station gateway.
 2. The first device of claim 1, wherethe one or more processors are further to: determine that the handoverfrom the first base station to the second base station is appropriatebased on one or more factors, the one or more factors including at leastone of: a utilization of network resources, or a measured signal qualityof other base stations in comparison to a measured signal quality of thefirst base station; and where the one or more processors, when receivingthe request, are to: receive the request based on determining that thehandover is appropriate.
 3. The device of claim 1, where the identifieris a concatenation of: a public land mobile network identifier, a basestation identifier, and a cell identifier.
 4. The device of claim 1,where the one or more processors are further to: utilize a tracking areaidentifier to locate the second base station; and where the one or moreprocessors, when providing the handover information, are to: provide thehandover information after locating the second base station.
 5. Thefirst device of claim 1, where the one or more processors are furtherto: locate the particular small-scale base station gateway; and wherethe one or more processors, when providing the handover information, areto: provide the handover information to permit the particularsmall-scale base station gateway to utilize the handover information tolocate the second base station.
 6. The device of claim 1, where the oneor more processors, when providing the handover information, are to:provide the handover information to permit the particular small-scalebase station gateway to identify the second base station after providingthe handover information.
 7. The first device of claim 1, where the oneor more processors are further to: utilize a portion of the identifierto determine that the identifier is assigned to the particularsmall-scale base station gateway; and where the one or more processors,when providing the handover information, are to: provide the handoverinformation to the particular small-scale base station gateway to:permit the particular small-scale base station gateway to analyze theidentifier to identify the second base station, and permit theparticular small-scale base station gateway to provide the handoverinformation to the second base station based on the particularsmall-scale base station gateway identifying the second base station. 8.A non-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors of a first device, cause the one or moreprocessors to: receive a request for a handover of a mobile device froma first base station to a second base station, the first base stationbeing a first type of base station, and the request including handoverinformation, the handover information including an identifier,  theidentifier being a type of identifier used to identify base stations ofthe first type of base station and gateways of a second type of basestation; determine that the second base station is the second type ofbase station based on the identifier identifying a particular gateway ofthe second type of base station; determine, based on the identifier andbased on determining that the second base station is the second type ofbase station, that the second base station is connected to theparticular gateway, one or more small-scale base stations, including thesecond base station, being managed by the particular gateway and theparticular gateway and the first base station being managed by thedevice; and provide the handover information to the particular gatewaybased on determining that the second base station is connected to theparticular gateway.
 9. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions, when executed by the one ormore processors, further cause the one or more processors to: determinewhether the second base station is in a list of target base stations notdirectly connected to the particular gateway based on determining thatthe second base station is the second type of base station.
 10. Thenon-transitory computer-readable medium of claim 9, where the list oftarget base stations is a first list of base stations, and where thesecond base station is not in the first list of base stations; and wherethe one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: determine thatthe second base station is in a second list of base stations directlyconnected to the particular gateway; and route the request to the secondbase station based on determining that the second base station is in thesecond list of base stations.
 11. The non-transitory computer-readablemedium of claim 9, where the second base station is in the list oftarget base stations, and where the one or more instructions, whenexecuted by the one or more processors, further cause the one or moreprocessors to: route the request to a network device for ultimaterouting to a particular network device that provides control service tothe mobile device.
 12. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions, when executed by the one ormore processors, further cause the one or more processors to: determinethat the handover from the first base station to the second base stationis appropriate based on one or more factors, the one or more factorsincluding at least one of: a utilization of network resources, or ameasured signal quality of other base stations in comparison to ameasured signal quality of the first base station; and where the one ormore processors, when receiving the request, are to: receive the requestbased on determining that the handover is appropriate.
 13. Thenon-transitory computer-readable medium of claim 8, where the identifieris a concatenation of: a public land mobile network identifier, a basestation identifier, and a cell identifier.
 14. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: utilize a tracking area identifier to locate thesecond base station; and where the one or more processors, whenproviding the handover information, are to: provide the handoverinformation after locating the second base station.
 15. A method,comprising: receiving, by a device, a request for a handover of a mobiledevice from a first base station to a second base station, the requestincluding handover information, the handover information including anidentifier, the identifier being a type of identifier used to identifyat least macro-scale base stations and small-scale base stationgateways; determining, by the first device, that the second base stationis a small-scale base station based on the identifier identifying aparticular small-scale base station gateway; determining, by the device,based on the identifier, and based on determining that the second basestation is the small-scale base station, that the second base station isconnected to the particular small-scale base station gateway, one ormore small-scale base stations, including the second base station, beingmanaged by the particular small-scale base station gateway, and theparticular small-scale base station gateway and the first base stationbeing managed by the device; and providing, by the first device, thehandover information to the particular small-scale base station gatewaybased on determining that the second base station is connected to theparticular small-scale base station gateway.
 16. The method of claim 15,where the method further comprises: locating the particular small-scalebase station gateway; and where providing the handover informationcomprises: providing the handover information to permit the particularsmall-scale base station gateway to utilize the handover information tolocate the second base station.
 17. The method of claim 15, whereproviding the handover information comprises: providing the handoverinformation to permit the particular small-scale base station gateway todetermine the second base station after providing the handoverinformation.
 18. The method of claim 15, further comprising: utilizing aportion of the identifier to determine that the identifier is assignedto the particular small-scale base station gateway; and where providingthe handover information comprises: providing the handover informationto the particular small-scale base station gateway to: permit theparticular small-scale base station gateway to analyze the identifier toidentify the second base station, and permit the particular small-scalebase station gateway to provide the handover information to the secondbase station based on the particular small-scale base station gatewaydetermining the second base station.
 19. The method of claim 15, furthercomprising: determining whether the second base station is in a list oftarget base stations not directly connected to the particularsmall-scale base station gateway based on determining that the secondbase station is small scale base station.
 20. The method of claim 19,where the list of target base stations is a first list of base stations,and where the second base station is not in the first list of basestations; and where the method further comprises: determining that thesecond base station is in a second list of base stations directlyconnected to the particular small-scale base station gateway; androuting the request to the second base station based on determining thatthe second base station is in the second list of base stations.